License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //src:license-check

Status: ⚠️ Needs Review

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.4.2) and connecting to it...
INFO: Invocation ID: 92777781-4dde-43fa-bcf4-52a6edbec77f
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
WARNING: Target pattern parsing failed.
ERROR: Skipping '//src:license-check': no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
ERROR: no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
INFO: Elapsed time: 4.756s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

The created documentation from the pull request is available at: docu-html

potentially other module repos though

Then in general we cannot link it directly, but must go through aou-linkage-elements in e.g. reference integration where the modules come together. Or do we make the modules depend on each other? That would heavily contradict independent modules - if we want those in score.

potentially other module repos though

Then in general we cannot link it directly, but must go through aou-linkage-elements in e.g. reference integration where the modules come together. Or do we make the modules depend on each other? That would heavily contradict independent modules - if we want those in score.

The pr provides only the how not the why

potentially other module repos though

Then in general we cannot link it directly, but must go through aou-linkage-elements in e.g. reference integration where the modules come together. Or do we make the modules depend on each other? That would heavily contradict independent modules - if we want those in score.

Okay so I changed the scope to only implement support covers linking from requirements to AoU according to gd_req__req_linkage_aou.
This PR does not define cross-repo dependency behavior; integration-level cross-repo composition remains out of scope and should be handled separately to preserve the SW-Module -> S-CORE dependency direction from DR-001.